vev: Log where MGT received its signal from #4139
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nigoroll
reviewed
Jul 29, 2024
cartoush
force-pushed
the
sigint_origin_log
branch
from
5265875 to
36bc3d9
Compare
nigoroll
approved these changes
Aug 16, 2024
cartoush
force-pushed
the
sigint_origin_log
branch
2 times, most recently
from
b51c52d to
80ae6a3
Compare
|
bugwash: OK |
(OBE commit message removed during merge/rebase by @nigoroll)
nigoroll
force-pushed
the
sigint_origin_log
branch
from
80ae6a3 to
0fa9533
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes MGT log from which PID originates the signal it received.
It does that by adding the SIGINFO flag to sigaction in order to use
sa_sigactioninsead ofsa_handlerand grab thestruct siginfo_twhich contains the origin PID